doc: explicitly state that corepack will be removed in v25+#57747
Merged
nodejs-github-bot merged 2 commits intomainfrom Apr 7, 2025
Merged
doc: explicitly state that corepack will be removed in v25+#57747nodejs-github-bot merged 2 commits intomainfrom
nodejs-github-bot merged 2 commits intomainfrom
Conversation
Loading
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
12 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The generic "future versions of" Node.js is causing a confusion among corepack users.
Example nodejs/corepack#688 (comment)
This PR explicitly changes it to v25+ as agreed in TSC vote in nodejs/TSC#1697 (comment)